Repository navigation
Conversation
A PATCH_TEXT answer needs a content object and neither INDEX nor WORKTREE names one, so `yas git diff -p` failed with Unsupported. Use the null object ID for patches between two mutable endpoints.
This was referenced Sep 28, 2026
Coverage
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Stacked on #24; the diff shows only this change.
yas git diff -pbetween the index and the working tree failed with Unsupported. A text PATCH needs a content object, and neither INDEX nor WORKTREE has one.A patch between two mutable endpoints (INDEX, WORKTREE, EMPTY) now carries the null object ID, and
docs/design/git.mddocuments this.yas git diff -pwith no revisions prints a unified diff of the working tree against the index.Testing
PATCH_TEXTcase totyped_queries_cover_repository_reads_without_exposing_legacy_packets.Tag
@indentto continue the conversation here.